Clarify in README that v0.9 and v1.0 are withdrawn#80
Clarify in README that v0.9 and v1.0 are withdrawn#80jmarinho merged 1 commit intoFirmwareHandoff:mainfrom
Conversation
jmarinho
requested review from
a team,
apalos,
danh-arm,
manish-pandey-arm and
sjg20
| stages during platform initialization. | ||
|
|
||
| Note that versions 0.9 and 1.0 of this specification were deprecated and should not be used for product development. | ||
|
|
There was a problem hiding this comment.
I think all the changes should be in the status section below, which is no longer accurate at all. Also, those versions are withdrawn, not deprecated. I think you could also say this is due to a mismatch in the checksum algorithm in the spec versus implementations (at least in the commit message).
jmarinho
force-pushed
the
deprecate
branch
2 times, most recently
from
2d71d89 to
6b8da54
Compare
README.md
Outdated
| By the end of 2024, the spec will be considered stable and will be published | ||
| as version 1. From there on, backwards compatibility will be maintained. | ||
| As of November 2025, version 1.0 is withdrawn and should not be used. | ||
| Version 1.0 was withdrawn because products shipped with an TL header cheksum implementation that differed from the version 1.0 definition. |
README.md
Outdated
| @@ -53,5 +55,8 @@ coreboot, TF-A and Tianocore. Once this is done we will review the result to see | |||
| if any serious flaws have come to light, meaning that changes are needed. If | |||
| so, these will be undertaken in each project. | |||
There was a problem hiding this comment.
It looks like all the above paragraph can now be removed.
|
@jmarinho could you please add some details in the PR body? At the moment all I see is a change ID, which isn't particularly relevant on GitHub (unless I'm missing something). Just a comment about what the PR does and why, for the benefit of those who somehow end up here in future. |
Update Readme: - state that v1.0 is withdrawn - set expectations for v2.0 release timeline The version v.9 and v1.0 are withdrawn because products shipped with a TL header checksum implementation that differed from what was spec'd (implementations used sum-based checksum, whereas spec mandated xor). Change-Id: Ibff46e7d88fcec0b1f3352aa7cebd7f5a7204e47 Signed-off-by: Jose Marinho <jose.marinho@arm.com>
Done |
| if any serious flaws have come to light, meaning that changes are needed. If | ||
| so, these will be undertaken in each project. | ||
| As of November 2025, version 1.0 is withdrawn and should not be used. | ||
| Version 1.0 was withdrawn because products shipped with a TL header cheksum implementation that differed from the version 1.0 definition. |
There was a problem hiding this comment.
minor: I think this file generally tries to stick to an 80 column limit.
danh-arm
changed the title
Update the transfer list library to implement specification version 2.0, as versions 1.0 and 0.9 have been withdrawn [1]. The primary change is switching the checksum calculation from an XOR sum to a byte-wise sum. This aligns the implementation with the updated specification and with behavior already used in existing deployments. 1. FirmwareHandoff/firmware_handoff#80 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
5 participants
Update Readme:
- state that v1.0 is withdrawn
- set expectations for v2.0 release timeline
The version v.9 and v1.0 are withdrawn because products shipped
with a TL header checksum implementation that differed from what was
spec'd (implementations used sum-based checksum, whereas spec mandated
xor).
Change-Id: Ibff46e7d88fcec0b1f3352aa7cebd7f5a7204e47